fix: fix and upgrade Husky pre-commit, and add dev container config#1168
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
fix: fix and upgrade Husky pre-commit, and add dev container config
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
RembrandtK
changed the title
tmigone
approved these changes
May 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
1: Husky pre-commit checks were not working for me.
This fixes them for me, and does a Husky upgrade in the process.
Upgraded Husky produced warnings on pre-commit script, changes there are to solve these and get it working.
2: Dev container configuration.
I use this for local development in a dev container. Might be of some use for others too.